hotfix: cherry-pick PDP course duplicate handling fix (#217)#220
Merged
Conversation
fix: fix duplicate-handling step in validation
Collaborator
|
Shoot I think there's a protection on the source branch. |
vishpillai123
approved these changes
Mar 23, 2026
Collaborator
|
Looks like we can still merge though |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
changes
fix/pdp-course-handling-duplicates) ontostaging: ensureschema_typeis passed through tohandling_duplicatesfor PDP course CSV validation, plus the associated ruff formatting on the PDP course read-path test.developintostaging.context
developalready had this PDP duplicate-handling fix;stagingneeded the same behavior without pulling unrelateddevelopchanges. Direct pushes tostagingare blocked by branch protection, so this lands via PR.questions